Check for LLVM and Rust objcopy binaries before throwing#312
Merged
arihant2math merged 1 commit intoJun 11, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
qemu_runner.pyfile hardcodedaarch64-none-elf-objcopyfor theobjcopybinary, which is distributed as part of the Arm GNU toolchain, and isn't available by default on macOS. LLVM ships with its own objcopy binary that has support for multiple targets and is described as a "drop-in replacement for GNU's objcopy" (see: https://llvm.org/docs/CommandGuide/llvm-objcopy.html).The
qemu_runner.pynow checks if the system hasllvm-objcopyandrust-objcopy(cargo wrapper overllvm-objcopy) and invokes whichever one it finds. If it doesn't find any, it throws an error instructing the programmer to install any of the above objcopy binaries.